Multi-Interface Transponder Device - Altering Power Modes

ABSTRACT

Methods for performing power management of a multi-interface transponder (MIT) device, e.g., such as positional tag device. The MIT device may transition between various power states, e.g., based on detected events, such as detecting movement of the MIT device, receiving a wakeup signal, receiving an indication of a transition in transportation mode, and/or detecting that the MIT device may be lost, such as based on a lack of contact with another device for more than a threshold period of time.

PRIOIRTY DATA

This application claims benefit of priority to U.S. ProvisionalApplication Ser. No. 62/810,492, titled “Multi-Interface TransponderDevice”, filed Feb. 26, 2019, which is hereby incorporated by referencein its entirety as though fully and completely set forth herein.

FIELD

The present application relates to wireless communications, includingtechniques for the design and operation of a multi-interface radiofrequency transponder device (or “tag”).

DESCRIPTION OF THE RELATED ART

Positional tags, such as electronic tracking devices, have creatednumerous ways for users to track locations of associated people and/orobjects. For example, global positioning system (GPS) technology can beused to determine the location of a tagged object associated with aperson, and the location can be communicated to another device. As afurther example, a positional tag could be attached to an item ofimportance (e.g., keys, wallet, briefcase, article of clothing,backpack, computing device, item of identification, and so forth) andvia communication with a companion device (e.g., phone, tablet, laptopcomputer, Internet of Things (IoT) device, and so forth), the positionaltag could update the location of the item of importance and help withrecovery if the item is missing.

Traditional positional tags (or tracking devices) and correspondingsystems typically suffer from one or more disadvantages. For example,communicating with a positional tag outside of near field communicationsrequires, relative to the form factor, a considerable amount of power.Thus, battery life of positional tags is often limited. In addition,long-range communication for such a device is relatively expensive andoften requires sophisticated circuitry for operating in connection withan associated electronic device (e.g., a mobile device). Additionally,low-power options for positional tags are often limited to communicatingwith nearby objects that may require a user associated with the trackingdevice(s) to be within a close proximity (e.g., near field) of thepositional tags, limiting the usefulness of such devices.

SUMMARY

Embodiments described herein relate to a multi-interface transponder(MIT) device, e.g., such as positional tag device. Additionally,embodiments described herein relate to power management of MIT devicesas well as various applications of such devices. Some embodiments relateto a wireless station configured to communicate with an MIT device,e.g., to determine and/or update location of the MIT device with alocation server and/or to aid a user of an MIT device to physicallylocate the MIT device when misplaced and/or lost.

In some embodiments, an MIT device may be configured to determine, whileoperating in a first power state, to transition to a second power statebased, at least in part, on detection of an event. In some embodiments,the event may be detectable via one of a first interface or motionsensing circuitry of the MIT device. Further, while operating in thesecond power state, the MIT device may be configured to transmit one ormore beacons via one of a second interface or a third interface of theMIT device. In some embodiments, selection of the second interface orthe third interface may be based, at least in part, on the event. Insome embodiments, the first interface may be an ultra-low power radiofrequency (RF) interface (e.g., such as a wake-up radio and/or wake-upreceiver), the second interface may be a Bluetooth interface, and thethird interface may be an ultra-wideband (UWB) RF interface. In someembodiments, the first power state may be associated with a low powerconsumption (e.g., sleep) state whereas the second power state may beassociated with a higher power consumption state. For example, thesecond state may be associated with transmission of Bluetooth beacons(or signals) at a first or second rate and/or associated withtransmission of UWB beacons (or signals). In some embodiments, the MITdevice may be configured to receive, from a neighboring wireless device,an indication that a location associated with the MIT device has beenupdated at a location server that may be associated with both theneighboring wireless device and the MIT device. Upon receiving theindication, the MIT device may be configured to transition, based, atleast in part, on the indication, to the first power state.

In some embodiments, an MIT device may be configured to enter a lowpower mode in which the second radio is disabled and receive, while inthe low power mode, a wake-up signal from a neighboring wireless device.In some embodiments, the wake-up signal may be received vialow-power/ultra low power (LP/ULP) communications. The MIT device may beconfigured to transmit, after transitioning to a higher power mode inresponse to receipt of the wake-up signal, beacons via the second radio.In some embodiments, the wakeup signal may indicate a transmission ratethat may be based, at least in part, on one or more of a transportationmode detected by the neighboring wireless device and/or an expectedmedium congestion as detected by the neighboring wireless device. Insome embodiments, the wakeup signal may indicate a transmission powerthat may be based, at least in part, on one or more of a transportationmode detected by the neighboring wireless device and/or an expectedmedium congestion as detected by the neighboring wireless device. Insome embodiments, the second radio may comprise an ultra-wideband radio.

In some embodiments, an MIT device may be configured to operate in a lowpower mode in which an ultra-wide band (UWB) radio of the MIT device maybe disabled. The MIT device may be configured to receive, whileoperating in the low power mode, a wake-up signal from a neighboringwireless device and transition out of the low power mode and enable theUWB radio in response to receipt of the wake-up signal. In someembodiments, the wake-up signal may be received by an ultra-low powerradio, e.g., via ULP/LP communications with the neighboring wirelessdevice. The MIT device may be configured to transmit, via the UWB radio,location beacons to the neighboring wireless device. In someembodiments, the wakeup signal may be received via one of a Bluetoothradio or an ultra-low power radio (e.g., such as a wake-up radio and/orwake-up receiver) in communication with the at least one processor. Insome embodiments, the wakeup signal may indicate a transmission rate anda transmission power for the location beacons.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of the embodiments is consideredin conjunction with the following drawings.

FIG. 1 illustrates an example of a wireless communication system,according to some embodiments.

FIG. 2A illustrates an example of wireless devices communicating,according to some embodiments.

FIG. 2B illustrates an example simplified block diagram of a wirelessdevice, according to some embodiments.

FIG. 2C illustrates an example WLAN communication system, according tosome embodiments.

FIG. 3A illustrates an example simplified block diagram of a WLAN AccessPoint (AP), according to some embodiments.

FIG. 3B illustrates an example simplified block diagram of a wirelessstation (UE), according to some embodiments.

FIG. 3C illustrates an example simplified block diagram of a wirelessnode, according to some embodiments.

FIG. 4 illustrates an example simplified block diagram of a positionaltag device, according to some embodiments.

FIG. 5 illustrates an exemplary state diagram for various power modes ofa multi-interface transponder (MIT) device, according to someembodiments.

FIGS. 6A-6C illustrate examples of an MIT device updating location vianeighboring devices, according to some embodiments.

FIG. 7 illustrates a block diagram of an example of a method for powermanagement of a MIT device, according to some embodiments.

FIG. 8A illustrates an example of transmission cycles of amulti-interface transponder (MIT) device, according to some embodiments.

FIG. 8B illustrates an example of transmission power adjustments as afunction of time since last location update, according to someembodiments.

FIG. 9 illustrates a block diagram of an example of a method for powermanagement of an MIT device based on a detected condition, according tosome embodiments.

FIG. 10 illustrates a block diagram of an example of a method of powermanagement of an MIT device based on a detection of a transition intransportation mode, according to some embodiments.

FIGS. 11-14 illustrates block diagrams of examples of methods of MITdevice operation, according to some embodiments.

FIG. 15 illustrates a block diagram of an example of a method ofscanning for an MIT device, according to some embodiments.

While the features described herein are susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are herein described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION Acronyms

Various acronyms are used throughout the present application.Definitions of the most prominently used acronyms that may appearthroughout the present application are provided below:

UE: User Equipment

AP: Access Point

TX: Transmission/Transmit

RX: Reception/Receive

WURx: Wake up to receiver

UWB: Ultra-wideband

BT/BLE: BLUETOOTH™/BLUETOOTH™ Low Energy

LP/ULP: Low power/ultra-low power communications

LAN: Local Area Network

WLAN: Wireless LAN

RAT: Radio Access Technology

TTL: time to live

SU: Single user

MU: Multi user

Terminology

The following is a glossary of terms used in this disclosure:

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random-access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium mayinclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium may be located in a firstcomputer system in which the programs are executed, or may be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system may provide program instructions to the firstcomputer for execution. The term “memory medium” may include two or morememory mediums which may reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium may store program instructions (e.g., embodied as computerprograms) that may be executed by one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

Positional Tag (or tracking device)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications, such as communication with a neighboring or companiondevice to share, determine, and/or update a location of the positionaltag. Wireless communication can be via various protocols, including, butnot limited to, Bluetooth, Bluetooth Low Energy (BLE), Wi-Fi, ultra-wideband (UWB), and/or one or more proprietary communication protocols.

Mobile Device (or Mobile Station)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications using WLAN communication. Examples of mobile devicesinclude mobile telephones or smart phones (e.g., iPhone™, Android™-basedphones), and tablet computers such as iPad™Samsung Galaxy™, etc. Variousother types of devices would fall into this category if they includeWi-Fi or both cellular and Wi-Fi communication capabilities, such aslaptop computers (e.g., MacBook™), portable gaming devices (e.g.,Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™),portable Internet devices, and other handheld devices, as well aswearable devices such as smart watches, smart glasses, headphones,pendants, earpieces, etc. In general, the term “mobile device” can bebroadly defined to encompass any electronic, computing, and/ortelecommunications device (or combination of devices) which is easilytransported by a user and capable of wireless communication using WLANor Wi-Fi.

Wireless Device (or Wireless Station)—any of various types of computersystems devices which performs wireless communications using WLANcommunications. As used herein, the term “wireless device” may refer toa mobile device, as defined above, or to a stationary device, such as astationary wireless client or a wireless base station. For example, awireless device may be any type of wireless station of an 802.11 system,such as an access point (AP) or a client station (STA or UE). Furtherexamples include televisions, media players (e.g., AppleTV™, Roku™,Amazon FireTV™, Google Chromecast™, etc.), refrigerators, laundrymachines, thermostats, and so forth.

WLAN—The term “WLAN” has the full breadth of its ordinary meaning, andat least includes a wireless communication network or RAT that isserviced by WLAN access points and which provides connectivity throughthese access points to the Internet. Most modern WLANs are based on IEEE802.11 standards and are marketed under the name “Wi-Fi”. A WLAN networkis different from a cellular network.

Processing Element—refers to various implementations of digitalcircuitry that perform a function in a computer system. Additionally,processing element may refer to various implementations of analog ormixed-signal (combination of analog and digital) circuitry that performa function (or functions) in a computer or computer system. Processingelements include, for example, circuits such as an integrated circuit(IC), ASIC (Application Specific Integrated Circuit), portions orcircuits of individual processor cores, entire processor cores,individual processors, programmable hardware devices such as a fieldprogrammable gate array (FPGA), and/or larger portions of systems thatinclude multiple processors.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thus,the term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, e.g., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Concurrent—refers to parallel execution or performance, where tasks,processes, signaling, messaging, or programs are performed in an atleast partially overlapping manner. For example, concurrency may beimplemented using “strong” or strict parallelism, where tasks areperformed (at least partially) in parallel on respective computationalelements, or using “weak parallelism”, where the tasks are performed inan interleaved manner, e.g., by time multiplexing of execution threads.

Configured to—Various components may be described as “configured to”perform a task or tasks. In such contexts, “configured to” is a broadrecitation generally meaning “having structure that” performs the taskor tasks during operation. As such, the component can be configured toperform the task even when the component is not currently performingthat task (e.g., a set of electrical conductors may be configured toelectrically connect a module to another module, even when the twomodules are not connected). In some contexts, “configured to” may be abroad recitation of structure generally meaning “having circuitry that”performs the task or tasks during operation. As such, the component canbe configured to perform the task even when the component is notcurrently on. In general, the circuitry that forms the structurecorresponding to “configured to” may include hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

Approximately—refers to a value that is almost correct or exact. Forexample, approximately may refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) may be applicationdependent. For example, in one embodiment, “approximately” may meanwithin 0.1% of some specified or desired value, while in various otherembodiments, the threshold may be, for example, 2%, 3%, 5%, and soforth, as desired or as required by the particular application.

FIG. 1—Wireless Communication System

FIG. 1 illustrates an example wireless communication system, accordingto some embodiments. It is noted that the system of FIG. 1 is merely oneexample of a possible system, and embodiments of this disclosure may beimplemented in any of various systems, as desired. As shown, theexemplary system 100 includes a plurality of wireless client stations ordevices, or user equipment (UEs), 106 that are configured to communicatewirelessly with various components within the system 100, such as anAccess Point (AP) 112, other client stations 106, wireless nodes 107,and/or positional tag devices 108. Some implementations can include oneor more base stations in addition to, or in place of, AP 112. The AP 112may be a Wi-Fi access point and may include one or more otherradios/access technologies (e.g., Bluetooth (BT), ultra-wide band (UWB),etc.) for wirelessly communicating with the various components of system100. The AP 112 may communicate via wired and/or wireless communicationchannels with one or more other electronic devices (not shown) and/oranother network, such as the Internet. The AP 112 may be configured tooperate according to any of various communications standards, such asthe various IEEE 802.11 standards as well as one or more proprietarycommunication standards, e.g., based on wideband, ultra-wideband, and/oradditional short range/low power wireless communication technologies. Insome embodiments, at least one client station 106 may be configured tocommunicate directly with one or more neighboring devices (e.g., otherclient stations 106, wireless nodes 107, and/or positional tag devices108), without use of the access point 112 (e.g., peer-to-peer (P2P) ordevice-to-device (D2D)). As shown, wireless node 107 may be implementedas any of a variety of devices, such as wearable devices, gamingdevices, and so forth. In some embodiments, wireless node 107 may bevarious Internet of Things (IoT) devices, such as smart appliances(e.g., refrigerator, stove, oven, dish washer, clothes washer, clothesdryer, and so forth), smart thermostats, and/or other home automationdevices (e.g., such as smart electrical outlets, smart lightingfixtures, and so forth).

As shown, a positional tag device 108 may communicate with one or moreother components within system 100. In some embodiments, positional tagdevice 108 may be associated with a companion device (e.g., a clientstation 106) and additionally be capable of communicating with one ormore additional devices (e.g., other client stations 106, wireless nodes107, AP 112). In some embodiments, communication with the companiondevice may be via one or more access technologies/protocols, such asBLUETOOTH™ (and/or BLUETOOTH™ (BT) Low Energy (BLE)), Wi-Fi peer-to-peer(e.g., Wi-Fi Direct, Neighbor Awareness Networking (NAN), and so forth),millimeter wave (mmWave) (e.g., 60 GHz, such as 802.11 ad/ay), as wellas any of various proprietary protocols (e.g., via wideband orultra-wideband (UWB) and/or low and/or ultra-low power (LP/ULP) wirelesscommunication). In some embodiments, communication with additionaldevices may be via BT/BLE as well as one or more other short-rangepeer-to-peer wireless communication techniques (e.g., various near-fieldcommunication (NFC) techniques, RFID, NAN, Wi-Fi Direct, UWB, LT/ULP,and so forth). In some embodiments, positional tag device 108 may becapable of updating a server with a current location (e.g., determinedby tag device 108 and/or provided to tag device 108 from another device)via the one or more additional devices as well as via the companiondevice.

FIGS. 2A-2B—Wireless Communication System

FIG. 2A illustrates an exemplary (and simplified) wireless communicationsystem in which aspects of this disclosure may be implemented. It isnoted that the system of FIG. 2A is merely one example of a possiblesystem, and embodiments of this disclosure may be implemented in any ofvarious systems, as desired.

As shown, the exemplary wireless communication system includes a(“first”) wireless device 105 in communication with another (“second”)wireless device 108. The first wireless device 105 and the secondwireless device 108 may communicate wirelessly using any of a variety ofwireless communication techniques.

As one possibility, the first wireless device 105 and the secondwireless device 108 may perform communication using wireless local areanetworking (WLAN) communication technology (e.g., IEEE 802.11/Wi-Fibased communication) and/or techniques based on WLAN wirelesscommunication. One or both of the wireless device 105 and the wirelessdevice 108 may also (or alternatively) be capable of communicating viaone or more additional wireless communication protocols, such as any ofBLUETOOTH™ (BT), BLUETOOTH™ Low Energy (BLE), near field communication(NFC), RFID, UWB, LP/ULP, GSM, UMTS (WCDMA, TDSCDMA), LTE, LTE-Advanced(LTE-A), NR, 3GPP2 CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), Wi-MAX,GPS, etc.

The wireless devices 105 and 108 may be any of a variety of types ofwireless device. As one possibility, wireless device 105 may be asubstantially portable wireless user equipment (UE) device, such as asmart phone, hand-held device, a laptop computer, a wearable device(such as a smart watch), a tablet, a motor vehicle, or virtually anytype of wireless device. As another possibility, wireless device 105 maybe a substantially stationary device, such as a payment kiosk/paymentdevice, point of sale (POS) terminal, set top box, media player (e.g.,an audio or audiovisual device), gaming console, desktop computer,appliance, door, access point, base station, or any of a variety ofother types of device. The wireless device 108 may be a positional tagdevice, e.g., in a stand-alone form factor, associated with, attachedto, and/or otherwise integrated into another computing device, and/orassociated with, attached to, and/or integrated into a personal articleor device (e.g., a wallet, a backpack, luggage, a briefcase, a purse, akey ring/chain, personal identification, and so forth) and/or acommercial article (e.g., a shipping container, shipping/storage pallet,an item of inventory, a vehicle, and so forth).

Each of the wireless devices 105 and 108 may include wirelesscommunication circuitry configured to facilitate the performance ofwireless communication, which may include various digital and/or analogradio frequency (RF) components, one or more processors configured toexecute program instructions stored in memory, one or more programmablehardware elements such as a field-programmable gate array (FPGA), aprogrammable logic device (PLD), an application specific IC (ASIC),and/or any of various other components. The wireless device 105 and/orthe wireless device 108 may perform any of the method embodiments oroperations described herein, or any portion of any of the methodembodiments or operations described herein, using any or all of suchcomponents.

Each of the wireless devices 105 and 108 may include one or moreantennas and corresponding radio frequency front-end circuitry forcommunicating using one or more wireless communication protocols. Insome cases, one or more parts of a receive and/or transmit chain may beshared between multiple wireless communication standards; for example, adevice might be configured to communicate using BT/BLE or Wi-Fi usingpartially or entirely shared wireless communication circuitry (e.g.,using a shared radio or one or more shared radio components). The sharedcommunication circuitry may include a single antenna, or may includemultiple antennas (e.g., for MIMO) for performing wirelesscommunications. Alternatively, a device may include separate transmitand/or receive chains (e.g., including separate antennas and other radiocomponents) for each wireless communication protocol with which it isconfigured to communicate. As a further possibility, a device mayinclude one or more radios or radio components that are shared betweenmultiple wireless communication protocols, and one or more radios orradio components that are used exclusively by a single wirelesscommunication protocol. For example, a device might include a sharedradio for communicating using one or more of LTE, CDMA2000 1×RTT, GSM,and/or 5G NR, and one or more separate radios for communicating usingWi-Fi and/or BT/BLE. Other configurations are also possible.

As previously noted, aspects of this disclosure may be implemented inconjunction with the wireless communication system of FIG. 2A. Forexample, a wireless device (e.g., either of wireless devices 105 or 108)may be configured to implement (and/or assist in implementation of) themethods described herein.

FIG. 2B illustrates an exemplary wireless device 110 (e.g.,corresponding to wireless devices 105 and/or 108) that may be configuredfor use in conjunction with various aspects of the present disclosure.The device 110 may be any of a variety of types of device and may beconfigured to perform any of a variety of types of functionality. Thedevice 110 may be a substantially portable device or may be asubstantially stationary device, potentially including any of a varietyof types of device. The device 110 may be configured to perform any ofthe techniques or features illustrated and/or described herein,including with respect to any or all of the Figures.

As shown, the device 110 may include a processing element 121. Theprocessing element may include or be coupled to one or more memoryelements. For example, the device 110 may include one or more memorymedia (e.g., memory 111), which may include any of a variety of types ofmemory and may serve any of a variety of functions. For example, memory111 could be RAM serving as a system memory for processing element 121.Additionally or alternatively, memory 111 could be ROM serving as aconfiguration memory for device 110. Other types and functions of memoryare also possible.

Additionally, the device 110 may include wireless communicationcircuitry 131. The wireless communication circuitry may include any of avariety of communication elements (e.g., antenna for wirelesscommunication, analog and/or digital communicationcircuitry/controllers, etc.) and may enable the device to wirelesslycommunicate using one or more wireless communication protocols.

Note that in some cases, the wireless communication circuitry 131 mayinclude its own processing element(s) (e.g., a baseband processor),e.g., in addition to the processing element 121. For example, theprocessing element 121 may be an ‘application processor’ whose primaryfunction may be to support application layer operations in the device110, while the wireless communication circuitry 131 may be a ‘basebandprocessor’ whose primary function may be to support baseband layeroperations (e.g., to facilitate wireless communication between thedevice 110 and other devices) in the device 110. In other words, in somecases the device 110 may include multiple processing elements (e.g., maybe a multi-processor device). Other configurations (e.g., instead of orin addition to an application processor/baseband processorconfiguration) utilizing a multi-processor architecture are alsopossible.

The device 110 may additionally include any of a variety of othercomponents (not shown) for implementing device functionality, dependingon the intended functionality of the device 110, which may includefurther processing and/or memory elements (e.g., audio processingcircuitry), one or more power supply elements (which may rely on batterypower and/or an external power source) user interface elements (e.g.,display, speaker, microphone, camera, keyboard, mouse, touchscreen,etc.), and/or any of various other components.

The components of the device 110, such as processing element 121, memory111, and wireless communication circuitry 131, may be operatively (orcommunicatively) coupled via one or more interconnection interfaces,which may include any of a variety of types of interface, possiblyincluding a combination of multiple types of interfaces. As one example,a USB high-speed inter-chip (HSIC) interface may be provided forinter-chip communications between processing elements. Alternatively (orin addition), a universal asynchronous receiver transmitter (UART)interface, a serial peripheral interface (SPI), inter-integrated circuit(I2C), system management bus (SMBus), and/or any of a variety of othercommunication interfaces may be used for communications between variousdevice components. Other types of interfaces (e.g., intra-chipinterfaces for communication within processing element 121, peripheralinterfaces for communication with peripheral components within orexternal to device 110, etc.) may also be provided as part of device110.

FIG. 2C—WLAN System

FIG. 2C illustrates an example WLAN system according to someembodiments. As shown, the exemplary WLAN system includes a plurality ofwireless client stations or devices, or user equipment (UEs), 106 thatare configured to communicate over a wireless communication channel 142with an Access Point (AP) 112. In some embodiments, the AP 112 may be aWi-Fi access point. The AP 112 may communicate via wired and/or wirelesscommunication channel(s) 150 with one or more other electronic devices(not shown) and/or another network 152, such as the Internet. Additionalelectronic devices, such as the remote device 154, may communicate withcomponents of the WLAN system via the network 152. For example, theremote device 154 may be another wireless client station. The WLANsystem may be configured to operate according to any of variouscommunications standards, such as the various IEEE 802.11 standards. Insome embodiments, at least one wireless device 106 is configured tocommunicate directly with one or more neighboring mobile devices, suchas positional tag devices 108, without use of the access point 112.

Further, in some embodiments, as further described below, a wirelessdevice 106 (which may be an exemplary implementation of device 110) maybe configured to perform (and/or assist in performance of) the methodsdescribed herein.

FIG. 3A—Access Point Block Diagram

FIG. 3A illustrates an exemplary block diagram of an access point (AP)112, which may be one possible exemplary implementation of the device110 illustrated in FIG. 2B. It is noted that the block diagram of the APof FIG. 3A is only one example of a possible system. As shown, the AP112 may include processor(s) 204, which may execute program instructionsfor the AP 112. The processor(s) 204 may also be coupled (directly orindirectly) to memory management unit (MMU) 240, which may be configuredto receive addresses from the processor(s) 204 and to translate thoseaddresses into locations in memory (e.g., memory 260 and read onlymemory (ROM) 250) or to other circuits or devices.

The AP 112 may include at least one network port 270. The network port270 may be configured to couple to a wired network and provide aplurality of devices, such as mobile devices 106, access to theInternet. For example, the network port 270 (or an additional networkport) may be configured to couple to a local network, such as a homenetwork or an enterprise network. For example, port 270 may be anEthernet port. The local network may provide connectivity to one or moreadditional networks, such as the Internet.

The AP 112 may include at least one antenna 234 and wirelesscommunication circuitry 230, which may be configured to operate as awireless transceiver and may be further configured to communicate withmobile device 106 (as well as positional tag device 108). The antenna234 communicates with the wireless communication circuitry 230 viacommunication chain 232. Communication chain 232 may include one or morereceive chains and/or one or more transmit chains. The wirelesscommunication circuitry 230 may be configured to communicate via Wi-Fior WLAN, e.g., 802.11. The wireless communication circuitry 230 mayalso, or alternatively, be configured to communicate via various otherwireless communication technologies, including, but not limited to,BT/BLE, UWB, and/or LP/ULP. Further, in some embodiments, the wirelesscommunication circuitry 230 may also, or alternatively, be configured tocommunicate via various other wireless communication technologies,including, but not limited to, Long-Term Evolution (LTE), LTE Advanced(LTE-A), Global System for Mobile (GSM), Wideband Code Division MultipleAccess (WCDMA), CDMA2000, etc., for example when the AP is co-locatedwith a base station in case of a small cell, or in other instances whenit may be desirable for the AP 112 to communicate via various differentwireless communication technologies.

Further, in some embodiments, as further described below, AP 112 may beconfigured to perform (and/or assist in performance of) the methodsdescribed herein.

FIG. 3B—Client Station Block Diagram

FIG. 3B illustrates an example simplified block diagram of a clientstation 106, which may be one possible exemplary implementation of thedevice 110 illustrated in FIG. 2B. According to embodiments, clientstation 106 may be a user equipment (UE) device, a mobile device ormobile station, and/or a wireless device or wireless station. As shown,the client station 106 may include a system on chip (SOC) 300, which mayinclude portions for various purposes. The SOC 300 may be coupled tovarious other circuits of the client station 106. For example, theclient station 106 may include various types of memory (e.g., includingNAND flash 310), a connector interface (UF) (or dock) 320 (e.g., forcoupling to a computer system, dock, charging station, etc.), thedisplay 360, cellular communication circuitry 330 such as for LTE, GSM,etc., short to medium range wireless communication circuitry 329 (e.g.,Bluetooth™ and WLAN circuitry), low power/ultra-low power (LP/ULP) radio339, and ultra-wideband radio 341. The client station 106 may furtherinclude one or more smart cards 310 that incorporate SIM (SubscriberIdentity Module) functionality, such as one or more UICC(s) (UniversalIntegrated Circuit Card(s)) cards 345. The cellular communicationcircuitry 330 may couple to one or more antennas, such as antennas 335and 336 as shown. The short to medium range wireless communicationcircuitry 329 may also couple to one or more antennas, such as antennas337 and 338 as shown. LP/ULP radio 339 may couple to one or moreantennas, such as antennas 347 and 348 as shown. Additionally, UWB radio341 may couple to one or more antennas, such as antennas 345 and 346.Alternatively, the radios may share one or more antennas in addition to,or instead of, coupling to respective antennas or respective sets ofantennas. Any or all of the radios may include multiple receive chainsand/or multiple transmit chains for receiving and/or transmittingmultiple spatial streams, such as in a multiple-input multiple output(MIMO) configuration.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the client station 106 and display circuitry304, which may perform graphics processing and provide display signalsto the display 360. The SOC 300 may also include motion sensingcircuitry 370, which may detect motion of the client station 106, forexample using a gyroscope, accelerometer, and/or any of various othermotion sensing components. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses intolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, cellular communication circuitry 330, short rangewireless communication circuitry 329, LP/ULP communication circuitry339, UWB communication circuitry 341, connector interface (UF) 320,and/or display 360. The MMU 340 may be configured to perform memoryprotection and page table translation or set up. In some embodiments,the MMU 340 may be included as a portion of the processor(s) 302.

As noted above, the client station 106 may be configured to communicatewirelessly directly with one or more neighboring client stations and/orone or more positional tag devices 108. The client station 106 may beconfigured to communicate according to a WLAN RAT for communication in aWLAN network, such as that shown in FIG. 2C. Further, in someembodiments, as further described below, client station 106 may beconfigured to perform (and/or assist in performance of) the methodsdescribed herein.

As described herein, the client station 106 may include hardware and/orsoftware components for implementing the features described herein. Forexample, the processor 302 of the client station 106 may be configuredto implement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 302 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 302 of the UE 106, in conjunction with one ormore of the other components 300, 304, 306, 310, 320, 329, 330, 335,336, 337, 338, 339, 340, 341, 345, 346, 347, 348, 350, and/or 360 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 204.

Further, as described herein, cellular communication circuitry 330 andshort-range wireless communication circuitry 329 may each include one ormore processing elements. Thus, each of cellular communication circuitry330 and short-range wireless communication circuitry 329 may include oneor more integrated circuits (ICs) configured to perform the functions ofcellular communication circuitry 330 and short-range wirelesscommunication circuitry 329, respectively.

FIG. 3C—Wireless Node Block Diagram

FIG. 3C illustrates one possible block diagram of a wireless node 107,which may be one possible exemplary implementation of the device 110illustrated in FIG. 2B. As shown, the wireless node 107 may include asystem on chip (SOC) 301, which may include portions for variouspurposes. For example, as shown, the SOC 301 may include processor(s)303 which may execute program instructions for the wireless node 107,and display circuitry 305 which may perform graphics processing andprovide display signals to the display 361. The SOC 301 may also includemotion sensing circuitry 371 which may detect motion of the wirelessnode 107, for example using a gyroscope, accelerometer, and/or any ofvarious other motion sensing components. The processor(s) 303 may alsobe coupled to memory management unit (MMU) 341, which may be configuredto receive addresses from the processor(s) 303 and translate thoseaddresses to locations in memory (e.g., memory 307, read only memory(ROM) 351, flash memory 311). The MMU 341 may be configured to performmemory protection and page table translation or set up. In someembodiments, the MMU 341 may be included as a portion of theprocessor(s) 303.

As shown, the SOC 301 may be coupled to various other circuits of thewireless node 107. For example, the wireless node 107 may includevarious types of memory (e.g., including NAND flash 311), a connectorinterface 321 (e.g., for coupling to a computer system, dock, chargingstation, etc.), the display 361, and wireless communication circuitry(radio) 381 (e.g., for LTE, LTE-A, CDMA2000, Bluetooth, Wi-Fi, NFC, GPS,UWB, LP/ULP, etc.).

The wireless node 107 may include at least one antenna, and in someembodiments, multiple antennas 387 and 388, for performing wirelesscommunication with base stations and/or other devices. For example, thewireless node 107 may use antennas 387 and 388 to perform the wirelesscommunication. As noted above, the wireless node 107 may in someembodiments be configured to communicate wirelessly using a plurality ofwireless communication standards or radio access technologies (RATs).

The wireless communication circuitry (radio) 381 may include Wi-Fi Logic382, a Cellular Modem 383, BT/BLE Logic 384, UWB logic 385, and LP/ULPlogic 386. The Wi-Fi Logic 382 is for enabling the wireless node 107 toperform Wi-Fi communications, e.g., on an 802.11 network and/or viapeer-to-peer communications (e.g., NAN). The BT/BLE Logic 384 is forenabling the wireless node 107 to perform Bluetooth communications. Thecellular modem 383 may be capable of performing cellular communicationaccording to one or more cellular communication technologies. The UWBlogic 385 is for enabling the wireless node 107 to perform UWBcommunications. The LP/ULP logic 386 is for enabling the wireless node107 to perform LP/ULP communications. Some or all components of thewireless communication circuitry 381 may be used for communications witha positional tag device 108.

As described herein, wireless node 107 may include hardware and softwarecomponents for implementing embodiments of this disclosure. For example,one or more components of the wireless communication circuitry 381 ofthe wireless node 107 may be configured to implement part or all of themethods described herein, e.g., by a processor executing programinstructions stored on a memory medium (e.g., a non-transitorycomputer-readable memory medium), a processor configured as an FPGA(Field Programmable Gate Array), and/or using dedicated hardwarecomponents, which may include an ASIC (Application Specific IntegratedCircuit). For example, in some embodiments, as further described below,wireless node 107 may be configured to perform (and/or assist in theperformance of) the methods described herein.

FIG. 4: Positional Tag Device

FIG. 4 illustrates an example simplified block diagram of a positionaltag device 108, which may be one possible exemplary implementation ofthe device 110 illustrated in FIG. 2B. According to embodiments,positional tag device 108 may include a system on chip (SOC) 400, whichmay include one or more portions for performing one or more purposes (orfunctions or operations). The SOC 400 may be coupled to one or moreother circuits of the positional tag device 108. For example, thepositional tag device 108 may include various types of memory (e.g.,including NAND flash 410), a connector interface (UF) 420 (e.g., forcoupling to a computer system, dock, charging station, light (e.g., forvisual output), speaker (e.g., for audible output), etc.), a powersupply 425 (which may be non-removable, removable and replaceable,and/or rechargeable), and communication circuitry (radio) 451 (e.g.,BT/BLE, WLAN, LP/ULP, UWB).

The positional tag device 108 may include at least one antenna, and insome embodiments, multiple antennas 457 and 458, for performing wirelesscommunication with a companion device (e.g., client station 106,wireless node 107, AP 112, and so forth) as well as other wirelessdevices (e.g., client station 106, wireless node 107, AP 112, otherpositional tag devices 108, and so forth). In some embodiments, one ormore antennas may be dedicated for use with a single radio and/or radioprotocol. In some other embodiments, one or more antennas may be sharedacross two or more radios and/or radio protocols. The wirelesscommunication circuitry 451 may include any/all of UWB logic 452, LP/ULPlogic 453, and/or BT/BLE logic 454. In some embodiments, wirelesscommunication circuitry may optionally include logic for any otherprotocol(s), such as Wi-Fi logic and/or a cellular (e.g., LicenseAssisted Access (LAA)) logic. The BT/BLE logic 454 is for enabling thepositional tag device 108 to perform Bluetooth communications. The UWBlogic 452 is for enabling the positional tag device 108 to perform UWBcommunications. The LP/ULP logic 453 is for enabling the positional tagdevice 108 to perform LP/ULP communications. In some embodiments, thewireless communication circuitry 451 may include multiple receive chainsand/or multiple transmit chains for receiving and/or transmittingmultiple spatial streams, such as in a multiple-input multiple output(MIMO) configuration. The UWB logic 452, LP/ULP logic 453, and BT/BLElogic 454 each may be independently configured to perform unidirectionalor bidirectional communication.

As shown, the SOC 400 may include processor(s) 402, which may executeprogram instructions for the positional tag device 108. The SOC 400 mayalso include motion sensing circuitry 470, which may be configured todetect motion of the positional tag device 108, for example using agyroscope, accelerometer, and/or any of various other motion sensingcomponents. In some embodiments, a GPS receiver and associated circuitrymay be used in addition to or in place of other motion sensingcircuitry. The processor(s) 402 may also be coupled (directly orindirectly) to memory management unit (MMU) 440, which may be configuredto receive addresses from the processor(s) 402 and translate thoseaddresses into locations in memory (e.g., memory 406, read only memory(ROM) 450, NAND flash memory 410) and/or to other circuits or devices,such as the wireless communication circuitry 451. The MMU 440 may beconfigured to perform memory protection and page table translation orset up. In some embodiments, the MMU 440 may be included as a portion ofthe processor(s) 402.

As noted above, the positional tag device 108 may be configured tocommunicate wirelessly with one or more neighboring wireless devices. Insome embodiments, as further described below, positional tag device 108may be configured to perform (and/or assist in the performance of) themethods described herein.

Positional Tag Power Management

In some embodiments, a multi-interface transponder (MIT) device, such aspositional tag device 108, may include multiple power levels and/orpower modes. For example, FIG. 5 illustrates an exemplary state diagramfor various power modes of an MIT device, according to some embodiments.As shown, the MIT device may operate in any of various power modes, suchas a low power mode 502, an ultra-low power mode 504, a high power mode506, and/or an ultra-high power mode 508. Further, as shown, the MITdevice may transition (or switch) between any of the various modes. Thetransition between modes can be based on any factor or combination offactors, including one or more received signals, sensor data, timingdata, environmental data, activity data, location data, etc. Also, theMIT device can be configured to transition from a present mode directlyto any other available mode. However, in some implementations, atransition may include a succession through one or more interveningmodes. For example, the MIT device may transition between low power mode502 and any of ultra-low power mode 504 (e.g., via transition 510),higher power mode 506 (e.g., via transition 516), and/or ultra-highpower mode 508 (e.g., via transition 518). As another example, the MITdevice may transition between ultra-low power mode 504 and any of lowpower mode 502 (e.g., via transition 510), higher power mode 506 (e.g.,via transition 512), and/or ultra-high power mode 508 (e.g., viatransition 514). Similarly, the MIT device may transition between highpower mode 506 and any of low power mode 502 (e.g., via transition 516),ultra-low power mode 504 (e.g., via transition 512), and/or ultra-highpower mode 508 (e.g., via transition 520). Additionally, the MIT devicemay transition between ultra-high power mode 508 and any of low powermode 502 (e.g., via transition 518), ultra-low power mode 504 (e.g., viatransition 514), and/or high power mode 506 (e.g., via transition 520).

In some embodiments, the ultra-low power mode 504 may be associated withan LP/ULP interface and/or LP/ULP logic, e.g., as described above inreference to positional tag device 108. In some embodiments, the MITdevice may remain in the ultra-low power mode 504 until a triggeringevent. In some embodiments, the triggering event may cause the MITdevice to transition to a higher power mode of operation (e.g., any oflow power mode 508, high power mode 504, and/or ultra-high power mode508).

In some embodiments, the triggering event may be a receivedsignal/beacon from a neighboring device. In some embodiments, thewake-up signal/beacon may be specific to the MIT device or may be ageneric signal/beacon, e.g., that is applicable to a set of MIT devicesor to all MIT devices. In other words, the MIT device may receive awake-up signal/beacon from a neighboring device that intends to wake-upthe MIT device or the MIT device may receive a wake-up signal/beaconfrom a neighboring device that intends to wake-up any MIT device (or anyof a certain type(s) of MIT device) within reception range of thewake-up signal/beacon. In some embodiments, the wake-up signal may bereceived via LP/ULP communications. In some embodiments, the wake-upsignal may be received by an ultra-low power radio, e.g., via ULP/LPcommunications with the neighboring wireless device. In someembodiments, the wake-up signal/beacon may cause the MIT device totransition to a higher power mode of operation (e.g., any of low powermode 502, high power mode 504, and/or ultra-high power mode 508). Insome embodiments, transition from the ultra-low power mode 504 may beslowed (or delayed) based, at least in part, on one or more factors,such as current location zone of the MIT device and/or movement of acompanion device.

For example, if the MIT device determines that its current location iswithin a safe zone (e.g., such as user's home, a user's work, a user'scar, and/or a frequent location, such as a friend's or relative's home),the MIT device may delay, or may not invoke, a transition to a higherpower mode. As another example, if the MIT device determines that amovement of a companion device is similar to a movement of the MITdevice, the MIT device may determine a constant motion state and delay,or may not invoke, a transition to a higher power state.

Conversely, in some embodiments, transition from the ultra-low powermode 504 may be accelerated based, at least in part, on one or morefactors, such as a current location or location zone of the MIT device,and/or a current transport mode. For example, if the MIT devicedetermines (or is notified) that a transportation transition isoccurring or is about to occur (e.g., exiting a train, airplane, ferry,taxi and/or boarding a train, airplane, ferry, taxi), the MIT device mayaccelerate the transition to a higher power mode (e.g., implement thetransition even in the absence of another trigger, such as separationfrom a companion device).

In some embodiments, the triggering event may be the sensing of movementby the MIT device. For example, the MIT device may monitor movement,e.g., via motion sensing circuitry, and transition from the ultra-lowpower mode 504 to a higher power mode based, at least in part, onmovement of the MIT device. In some embodiments, the triggering eventmay be based, at least in part, on an elapsed time between locationupdates of the MIT device. In some embodiments, the elapsed time betweenlocation updates may be based, at least in part, on a location mode ofthe MIT device (e.g., safe zone mode, danger zone mode, lost mode, andso forth).

For example, based on the triggering event, the MIT device maytransition to the low power mode 502 and begin to transmit beaconsand/or scan for beacons at a first rate over a low power interface. Insome embodiments, the periodicity of beacon transmissions may beapproximately 1 to 2 seconds. In some other embodiments, the periodicityof beacon transmissions may be less than 1 second, 1-5 seconds, or morethan 5 seconds. In some embodiments, the beacons may be transmitted viaa BLE interface or via BLE logic. In some embodiments, a transmissionpower of the beacons may be based, at least in part, on a location modeof the MIT device and/or an elapsed time since the last location update.For example, in a safe zone mode, the MIT device may transmit beaconsless frequently upon wake-up and at a lower power level as compared to adanger zone mode, in which the MIT device may transmit beacons morefrequently upon wake-up and/or at a higher power level. In someembodiments, the MIT device may transition back to the ultra-low powermode 504 upon an acknowledgment of an updated location. In someembodiments, the MIT device may transition to one of high power mode 506and/or ultra-high power mode 508 depending on various criteria (e.g.,detection of entrance into a danger zone, instruction received fromcompanion device, movement detection, increasing separation from acompanion device, and so forth), prior to transitioning to ultra-lowpower mode 504.

As another example, based on the triggering event, the MIT device maytransition to the high power mode 506 and begin to transmit and/orreceive beacons at a second rate over a low power interface. In someembodiments, the periodicity of beacon transmissions may beapproximately 1 to 10 milliseconds. In some other embodiments, theperiodicity may be less than 1 millisecond, tens of milliseconds, orhundreds of milliseconds. In some embodiments, the beacons may betransmitted via a BLE interface or via BLE logic. In some embodiments, atransmission power of the beacons may be based, at least in part, on alocation mode of the MIT device and/or an elapsed time since lastlocation update. For example, in a safe zone mode, the MIT device maytransmit beacons less frequently upon wake-up and/or at a lower powerlevel, as compared to a danger zone mode, in which the MIT device maytransmit beacons more frequently upon wake-up and/or at a higher powerlevel. In some embodiments, the MIT device may transition back to theultra-low power mode 504 upon an acknowledgment of updated location. Insome embodiments, the MIT device may transition to one of low power mode502 and/or ultra-high power mode 508, depending on various criteria(e.g., detection of entrance into a danger zone, instruction receivedfrom a companion device, movement detection, separation from a companiondevice, and so forth), prior to transitioning to ultra-low power mode504.

As a further example, the MIT device may transition to the ultra-highpower mode 508 and begin to transmit beacons at a first rate over a highpower interface. In some embodiments, the beacons may be transmitted viaa UWB interface or via UWB logic. In some embodiments, the ultra-highpower mode 508 may be initiated when a companion device is seeking(e.g., attempting to precisely locate) the MIT device. In someembodiments, the MIT device may transition back to the ultra-low powermode 504 upon an acknowledgment of updated location. In someembodiments, the MIT device may transition to one of low power mode 502and/or ultra-high power mode 508 depending on various criteria (e.g.,detection of entrance into a danger zone, instruction received fromcompanion device, movement detection, and so forth), prior totransitioning to ultra-low power mode 504.

FIGS. 6A-6C illustrate examples of an MIT device updating location vianeighboring devices, according to some embodiments. As shown, an MITdevice 608 may be within range of one or more neighboring devices, suchas companion (or trusted) device 602 (e.g., a device that is associatedwith the MIT device, such as a device used to register the MIT devicewith a location server, such as location server 614) and/ornon-companion devices 604a and 604n (e.g., a device associated with alocation server, such as location server 614, but not a deviceassociated with the MIT device). The MIT device 608 may detect/sense atriggering event, such as triggering events 620, 630, or 640. Inresponse to the triggering event, the MIT device 608 may transition froman ultra-low power mode of operation to a higher power mode of operationand begin to transmit beacons/signals 610. Note that the periodicity,power, and type of beacon/signal transmitted by the MIT device 608 maybe based, at least in part, on a power mode of the MIT device. Thus, insome embodiments, beacons/signals 610 may be lower power beacons/signals(e.g., BLE beacons/signals) transmitted at a low rate (e.g.,approximately every 1 to 2 seconds), lower power beacons/signalstransmitted at a high rate (e.g., approximately every 1 to 10milliseconds), and/or higher power beacons/signals (e.g., UWBbeacons/signals).

For example, as illustrated by FIG. 6A, after triggering event 620, MITdevice 608 may transmit one or more beacons 610. At least one of thebeacons 610 may be received by a companion device 602. Upon receipt ofthe at least one beacon 610, companion device 602 may exchangecommunications 622 with the MIT device 608. Based on the communications622, companion device 602 may update a location server 614 with anupdated location of MIT device 608 via communications 624 and 626. Insome embodiments, the communications 624 and 626 may be conveyed viapush notification connection with location server 614. Once the locationserver 614 has confirmed the updated location of MIT device 608, thecompanion device 602 may exchange one or more confirmation messages 628with MIT device 608. At 629, MIT device 608 may transition back to anultra-low power mode and/or to one or more other power modes, e.g., asdescribed above.

As another example, as illustrated by FIG. 6B, after triggering event630, MIT device 608 may transmit one or more beacons 610. At least oneof the beacons 610 may be received by a non-companion device 604a. Uponreceipt of the at least one beacon 610, non-companion device 604a mayexchange communications 632 with the MIT device 608. Based on thecommunications 632, non-companion device 604a may update a locationserver 614 with an updated location of MIT device 608 via communications634 and 636. In some embodiments, the communications 634 and 636 may beconveyed via push notification connection with location server 614. Oncethe location server 614 has confirmed the updated location of MIT device608, the non-companion device 604a may exchange one or more confirmationmessages 638 with MIT device 608. At 639, MIT device 608 may transitionback to an ultra-low power mode and/or to one or more other power modes,e.g., as described above.

As a further example, as illustrated by FIG. 6C, after triggering event640, MIT device 608 may transmit one or more beacons 610. At least oneof the beacons 610 may be received by a non-companion device 604n. Uponreceipt of the at least one beacon 610, non-companion device 604n mayexchange communications 642 with the MIT device 608. Based on thecommunications 642, non-companion device 604n may update a locationserver 614 with an updated location of MIT device 608 via communications644 and 646. In some embodiments, the communications 644 and 646 may beconveyed via push notification connection with location server 614. Oncethe location server 614 has confirmed the updated location of MIT device608, the non-companion device 604n may exchange one or more confirmationmessages 648 with MIT device 608. At 649, MIT device 608 may transitionback to an ultra-low power mode and/or to one or more other power modes,e.g., as described above.

FIG. 7 illustrates a block diagram of an example method for powermanagement of a multi-interface transponder (MIT) device, according tosome embodiments. The method shown in FIG. 7 may be used in conjunctionwith any of the systems or devices shown in the Figures, among otherdevices. In various embodiments, some of the method elements shown maybe performed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

At 702, an MIT device may determine, while in a first power state, totransition to a second power state based, at least in part, on detectionof an event. In some embodiments, the event may be detectable via aninterface, e.g., a first interface, and/or sensing circuitry, e.g.,motion sensing circuitry, of the MIT device. For example, in someembodiments, the event may include receiving (from a companion device,such as client station 106 and/or wireless node 107) a wakeup indicationvia the first interface. In some embodiments, the first interface may bean ultra-low power radio frequency (RF) interface (e.g., such as awake-up radio and/or wake-up receiver). In some embodiments, the eventmay include detecting movement (and/or a change in movement) of the MITdevice, e.g., greater than a threshold. Note that in some embodiments,the MIT device may ignore movement detected by the motion circuitry,e.g., if a companion device indicates that the movement is associatedwith a mode of transportation.

At 704, the MIT device may transition to the second power state. In someembodiments, transitioning to the second power state may includeactivating a second interface of the MIT device. In some embodiments,the second interface may be one of a Bluetooth interface and/or anultra-wideband (UWB) interface. In some embodiments, the MIT device maydetermine which interface to activate based, at least in part, on thedetected event.

At 706, the MIT device, while in the second power state, may transmitone or more beacons via a selected interface based, at least in part, onthe detected event. For example, when the event includes receiving awakeup indication, the wakeup indication may include instructions toactivate a specific interface. Additionally, in some embodiments, theinstructions may include one or more transmission intervals and/ortransmission powers. For example, the instructions may indicateactivation of a Bluetooth interface. Additionally, the instructions mayindicate a transmission rate (e.g., lower rate, on the order of everyone to two seconds, or a higher rate, e.g., on the order of every one to10 milliseconds). Further, the instructions may indicate a transmissionpower (e.g., based on congestion). As another example, the instructionsmay indicate activation of an ultra-wideband interface as well asassociated transmission frequency and/or transmission power information.

At 708, the MIT device, while in the second power state, may receive anindication of a location update from a neighboring wireless device. Insome embodiments, the neighboring wireless device may be a companiondevice (e.g., a device with a secure connection/secure relationship withthe MIT device). In some embodiments, the companion device may be awireless station, such as wireless station 106. In some embodiments, thecompanion device may a wireless node, such as wireless node 107. Notethat a companion device may also include a device that assisted the MITdevice in registration with a location server. In some embodiments, thecompanion device may support multiple MIT devices. In some embodiments,the neighboring wireless device may be a non-companion device (e.g., adevice without a secure connection/secure relationship with the MITdevice) associated with the location server. For example, thenon-companion device may be in communication with the location serverand may be configured to update locations of MIT devices not associatedwith the non-companion device. Thus, the non-companion device may assistwith updating the location of the MIT device, e.g., when (or if) the MITdevice is separated from (out of communication rage of) the companiondevice.

At 710, the MIT device may transition from the second power state to athird power state based, at least in part, on the indication. Forexample, in some embodiments, the indication may cause (or instruct) theMIT device to transition back to an ultra-low power state (e.g., such asultra-low power mode 504). Alternatively, the indication may cause (orinstruct) the MIT device to transition from a low transmission rate to ahigher transmission rate (e.g., from a low power state, such as lowpower mode 502, to a higher power state, such as high power mode 506).In some embodiments, the indication may cause activation and/ordeactivation of another interface. For example, the second power statemay include activation of a Bluetooth interface and transition to athird power state may cause activation of the ultra-wideband interface.Further, in some implementations, transition to the third power statemay cause de-activation of the Bluetooth interface. As another example,the second power state may include activation of a Bluetooth orultra-wideband interface and transition to the third power state mayinclude de-activation of the activated interface.

In some embodiments, power management of a multi-interface transponder(MIT) device, such as device 108, may be based, at least in part, on ageographic location zone and/or location mode, of the MIT device. Forexample, the MIT device may alter a power mode based, at least in part,on determining that the MIT device is lost, e.g., separated from acompanion device for more than a specified period of time. As anotherexample, the MIT device may alter a power mode based, at least in part,on determining that the MIT device is in (or within) a danger zone,e.g., during a transition in transportation mode, such as a trainstopping, a car stopping, a plane landing, a ferry docking, and soforth. As yet another example, the MIT device may consider multiplefactors, such as companion and location factors, with respect toaltering a power mode. As still another example, the MIT device mayalter a power mode based, at least in part, on determining that the MITdevice is in (or within) a safe zone, e.g., within a user's home, anoften-visited location of the user (such as a friend's or relative'shome, a place of work, and so forth).

For example, in some embodiments, a multi-interface transponder (MIT)device, e.g., such as positional tag device 108, may determine that itis lost, e.g., based on a duration of time since a last communicationwith a companion device. In some embodiments, the determination may befurther based, at least in part, on a duration of time since a locationupdate and/or receipt of a signal from a device associated with alocation server. In such instances, the MIT device may transition to apower state (or power mode) associated with a lost mode of operation. Insome embodiments, operating in the lost mode may include the MIT devicealtering and/or adjusting transmission power and/or transmission ratesto further conserve battery power and increase the probability ofdiscovery. For example, transmission rate may be based, at least inpart, on time of day as illustrated by FIG. 8A. As shown, the MIT devicemay transmit beacons at a higher rate during portions of daylight, e.g.,when it may be more likely to encounter a neighboring device. Inaddition, in some embodiments, the MIT device may cluster sets oftransmissions (e.g., transmission burst) within a short time frame whilespending a majority of a 24-hour cycle not transmitting (e.g., sleeping)to further conserve battery power. As another example, as illustrated byFIG. 8B, the MIT device may adjust transmission power, based, at leastin part, on the duration of time since receipt of a signal from a deviceassociated with a location server. For example, the MIT device mayincrease transmission power (e.g., to increase transmission range) asthe duration of time increases and/or during portions of daylight. Insome embodiments, the increase in transmission power may be offset by adecrease in transmission periodicity and/or transmission cycles tomaintain battery power, e.g., as illustrated by FIG. 8A. Further, insome embodiments, the transmission power may be incrementally increasedas the duration of time (e.g., since the last location update)increases, as shown in FIG. 8B. In some embodiments, after a timeperiod, the transmission power may be incrementally reduced to furtherconserve battery power. Note that as the time period (time since lastcontact) increases, transmission decisions (e.g., transmission rate,transmission frequency, transmission power, and so forth) by the MITdevice may be altered to prolong the battery life of the MIT device. Inother words, when the time period is within the range of hours, the MITdevice may adopt a different transmission pattern (e.g., most aggressivetransmission patterns, less regard for battery conservation) as comparedto when the period is within the range of days (aggressive transmissionpatterns, but some regard for battery conservation) or weeks (lessaggressive transmission patterns, more regard for battery longevity) ,or even months (most aggressive battery conservation, highlyconservative transmission patterns).

FIG. 9 illustrates a block diagram of another example of a method forpower management of a multi-interface transponder (MIT) device,according to some embodiments. The method shown in FIG. 9 may be used inconjunction with any of the systems or devices shown in the Figures,among other devices. In various embodiments, some of the method elementsshown may be performed concurrently, in a different order than shown, ormay be omitted. Additional method elements may also be performed asdesired. As shown, this method may operate as follows.

At 902, an MIT device, such as device 108, may determine a condition ofthe MIT device. In some embodiments, the condition may be based, atleast in part, on a duration of time since communication with acompanion device. In some embodiments, the condition may be furtherbased, at least in part, on a duration of time since the MIT devicereceived an indication that a location associated with the MIT devicehas been updated at a location server. In some embodiments, thecondition may be further based, at least in part, on a duration of timesince the MIT device has received a signal from a neighboring wirelessdevice, e.g., such as a wireless station 106, a wireless node 107,and/or an AP 112. In some embodiments, the condition may be associatedwith a determination that the MIT device is lost (e.g., separated from acompanion device).

At 904, the MIT device may transition to a first mode of operationbased, at least in part, on the condition. In some embodiments, the modeof operation may be associated with a lost mode of operation and may beconfigured to extend an operating life of the MIT device. For example,in some embodiments, the first mode of operation may include longportions of power conservation (e.g., sleep) followed by short bursts ofbeacon transmissions. In other words, the MIT device may transmitbeacons over a first interface (such as a Bluetooth interface) at a highrate for a first portion of time (e.g., a first portion of a 24-hourperiod) and spend the remaining portion of time in a power conservationstate. In some embodiments, the first portion of time may at leastpartially correspond to daylight hours (e.g., as sensed by a lightsensor of the MIT device or corresponding to a time kept by the MITdevice) to increase the probability of discovery. In some embodiments,the MIT device may, as the duration of time since the last locationupdate increases, increase transmit power in order to increase discoveryrange. Note that in some embodiments, since increasing transmit poweradversely effects power consumption, the MIT device may mitigate theincreased power consumption by decreasing a number of beaconstransmitted within a time period. Further, in some embodiments, the MITdevice may vary a frequency of transmissions (or cluster oftransmissions) in an attempt to discover a neighboring wireless device.

As another example, the MIT device may alter a power mode based, atleast in part, on determining that the MIT device is in (or within) adanger zone, e.g., during a transition in transportation mode, such as atrain stopping, a car stopping, a plane landing, a ferry docking, and soforth. In some embodiments, a companion device, e.g., such as clientstation 106 and/or wireless node 107, may determine a transportationmode (e.g., vehicle, plane, train, boat, and so forth). In addition, thecompanion device may monitor movement for a transition in thetransportation mode (e.g., vehicle stopping, plane landing, trainslowing, boat docking, and so forth) or location along a route (e.g.,approaching a known transition point or destination). Upon detection ofa transition in the transportation mode, the companion device may notifythe MIT device of the transition or signal a change in mode. In someembodiments, the MIT device may then alter its power mode to transmit ata higher rate and/or with higher transmission power.

For example, referring back to FIG. 5, during transportation, the MITdevice may be in the ultra-low power mode 504 and upon notification, maytransition to high power mode 506. In some embodiments, the MIT devicemay activate a Bluetooth interface and transmit beacons at a higher rate(e.g., approximately every 1 to 10 milliseconds). In some embodiments,if a distance between the MIT device and the companion device increasesbeyond approximately 1 meter (e.g., 2 to 3 feet), an alert ornotification (e.g., visual, audible, and/or haptic) may be output fromthe companion device. Additionally, the companion device may send aninstruction to the MIT device to transition to a higher power mode,e.g., to the ultra-high power mode 508 from high power mode 506. In someembodiments, the MIT device may activate an ultra-wide band interface toincrease precision of location detection. In some embodiments, the MITdevice also may deactivate the Bluetooth interface. Additionally, inareas of greater (e.g., above average) access medium congestion(interference) (e.g., danger zones), the companion device may transmitinstructions to supported MIT devices to further increase a locationupdate rate (e.g., in addition to increasing transmission rate and/ortransmission power). In some embodiments, the companion device mayincrease scan window length and/or scan window frequency in order tomitigate increased congestion (and/or interference caused by increasedaccess medium traffic). Note, that in some embodiments, the companiondevice may support multiple MIT devices. Thus, in some embodiments, thecompanion device may filter out beacons from non-supported MIT devices.

FIG. 10 illustrates a block diagram of another example method for powermode switching of a multi-interface transponder (MIT) device based ongeographic zone, according to some embodiments. The method shown in FIG.10 may be used in conjunction with any of the systems or devices shownin the Figures, among other devices. In various embodiments, some of themethod elements shown may be performed concurrently, in a differentorder than shown, or may be omitted. Additional method elements may alsobe performed as desired. As shown, this method may operate as follows.

At 1002, an MIT device, such as device 108, may receive an indication ofa transition in transportation mode. The indication may be received viaa first interface and from a companion device. The companion device maybe a UE device, such as client station 106, a wearable device, such aswireless node 107, and/or an access point device, such as AP 112. Thefirst interface may correspond to a first power state. Additionally, thefirst interface may be an ultra-low power radio frequency interface(e.g., such as a wake-up radio and/or wake-up receiver). In someembodiments, the transportation mode may include or indicate at leastone conveyance, e.g., a vehicle, a train, a boat, or a plane.

At 1004, the MIT device, in response to the indication, may transitionto a second power state. In some embodiments, the second power state maybe associated with activation of a second interface. The secondinterface may consume more power than the first interface. In someembodiments, the second interface may be one of a Bluetooth or anultra-wideband interface.

At 1006, the MIT device may transmit, via the second interface, one ormore beacons at a first transmission rate and at a first transmissionpower to the companion device. In some embodiments, the MIT device mayreceive, from the companion device, an indication of an end of thetransition in transportation mode. In response, the MIT device maytransition back to the first power state. In some instances, the MITdevice may receive, from the companion device, an indication that thecompanion device has moved more than a threshold distance from the MITdevice. In response, the MIT device may increase the first transmissionrate of the one or more beacons to a second transmission rate. In someembodiments, the threshold distance may be approximately 1 meter (e.g.,between 2 and 3 feet). In some embodiments, the MIT device may receive,from the companion device, an indication to increase transmission power.In some embodiments, the indication may be based, at least in part, ondetermining the presence of a higher level (e.g., above average) ofcongestion.

In some embodiments, a companion device, such as wireless station 106and/or wireless node 107, may use a last location of the multi-interfacetransponder (MIT) device, such as device 108, to aid a user inphysically discovering the MIT device, e.g., even when the MIT device isnot broadcasting to the companion device. For example, the companiondevice may send one or more signals to wake up the MIT device anddetermine a location of the MIT device (relative to the companiondevice) via ultra-wideband communications. Once the location of the MITdevice is determined, the MIT device may discontinue transmissions(e.g., transition to ultra-low power mode 504). For example, a sensor ofthe MIT device can detect that it has been located, e.g., throughmotion, etc. In addition, as part of finding the MIT, the companiondevice may display a map view and/or an augmented reality (AR) viewindicating location of the MIT device. In some embodiments, as thecompanion device is moved, the map view/AR view may be updated based onmovement of the companion device. In other words, location of the MITdevice relative to the companion device may be updated based, at leastin part, on movement of the companion device.

FIGS. 11-14 illustrate block diagrams of examples of methods of MIToperation, according to some embodiments. The methods shown in FIGS.11-14 may be used in conjunction with any of the systems or devicesshown in the Figures, among other devices. In various embodiments, someof the method elements shown may be performed concurrently, in adifferent order than shown, or may be omitted. Additional methodelements may also be performed as desired. As shown, these methods mayoperate as follows.

Turning to FIG. 11, at 1102, an MIT device (such as MIT device 108)having any/all of a low power radio interface (e.g., a wake-up radioand/or wake-up receiver), a medium power radio interface (e.g.,Bluetooth (BT) and/or Bluetooth Low Energy (BLE)), and/or a high powerradio interface (e.g., UWB, 60 GHz) may be in a low power mode ofoperation (e.g. operating in a low power mode of operation). In the lowpower mode, the MIT device, via the low power radio interface, mayperiodically scan for messages (e.g., beacons, polls, probes, etc.)addressed to the MIT device, which may signal the MIT device to activatea higher power radio interface. A message may be received from anassociated device (e.g., a paired device or a device associated with thesame or a related user account, such as wireless station 106, wirelessnode 107, and/or AP 112) or from an unassociated device (e.g., a deviceassociated with a different user account). In some embodiments, the MITdevice may not transmit regularly (e.g., continuously or periodically)while in the low power mode to conserve battery power. Further, the scanwindow period (e.g., the width of the window) and interval (e.g., theperiod between intervals) may be set or may be dynamically adjusted,e.g., in response to one or more factors, such as battery level,congestion/interference, time of day, sensor data, and so forth.Additionally, the MIT device may respond to a message addressed uniquelyto the MIT device, addressed to a group (or set) that includes the MITdevice, or addressed to all MIT devices. The MIT device also may ignoremessages that are not addressed to the MIT device, e.g., such asmessages uniquely addressed to a different MIT device or to a group towhich the MIT device does not belong.

At 1104, during a scan window, a message addressed to the MIT device maybe received from a wireless device via the low power interface. At 1106,in response, the MIT device may activate at least one higher powerinterface, such as a BT or BLE interface, and may establishcommunication with the wireless device, e.g., by transmitting aresponse. At 1108, through the communication, the MIT device can receiveupdated location information and/or one or more commands, such as acommand to activate a high power interface and/or to output one or moresignals (e.g., audible, visual, haptic).

At 1110, the MIT device may determine whether any remaining operationsare to be performed via a medium or high power interface. If noremaining operations are to be performed, the MIT device may deactivateall interfaces but the low power interface and may resume monitoringthrough scan windows.

Turning to FIG. 12, at 1202, an MIT device (such as MIT device 108)having any/all of a low power radio interface (e.g., a wake-up radioand/or wake-up receiver), a medium power radio interface (e.g.,Bluetooth (BT) and/or Bluetooth Low Energy (BLE)), and/or a high powerradio interface (e.g., UWB, 60 GHz) may be in a low power mode ofoperation (e.g. operating in a low power mode of operation). In the lowpower mode, the MIT device, via the low power radio interface, mayperiodically scan for messages (e.g., beacons, polls, probes, etc.)addressed to the MIT device, which may signal the MIT device to activatea higher power radio interface. A message may be received from anassociated device (e.g., a paired device or a device associated with thesame or a related user account, such as wireless station 106, wirelessnode 107, and/or AP 112) or from an unassociated device (e.g., a deviceassociated with a different user account). In some embodiments, the MITdevice may not transmit regularly (e.g., continuously or periodically)while in the low power mode to conserve battery power. Further, the scanwindow period (e.g., the width of the window) and interval (e.g., theperiod between intervals) may be set or may be dynamically adjusted,e.g., in response to one or more factors, such as battery level,congestion/interference, time of day, sensor data, and so forth.Additionally, the MIT device may respond to a message addressed uniquelyto the MIT device, addressed to a group (or set) that includes the MITdevice, or addressed to all MIT devices. The MIT device also may ignoremessages that are not addressed to the MIT device, e.g., such asmessages uniquely addressed to a different MIT device or to a group towhich the MIT device does not belong.

At 1204, the MIT device can detect motion through sensor data (e.g.,from an accelerometer or gyroscope). In some implementations, at 1206,the MIT device can activate another interface (e.g., BT/BLE) in responseto the motion and can output beacons periodically. The periodicity andnumber of beacons can depend on a variety of factors, includinglocation, the type of motion, the duration of the motion, proximity ofan associated device, etc.

At 1208, the MIT device can determine that the motion has ended and thatthe MIT device has performed a location update operation with anotherdevice (e.g., an associated device). Thereafter, the MIT device canreturn to a low power mode and resume monitoring through scan windows.

Turning to FIG. 13, at 1302, an MIT device (such as MIT device 108)having any/all of a low power radio interface (e.g., a wake-up radioand/or wake-up receiver), a medium power radio interface (e.g.,Bluetooth (BT) and/or Bluetooth Low Energy (BLE)), and/or a high powerradio interface (e.g., UWB, 60 GHz) may be in a low power mode ofoperation (e.g. operating in a low power mode of operation). In the lowpower mode, the MIT device, via the low power radio interface, mayperiodically scan for messages (e.g., beacons, polls, probes, etc.)addressed to the MIT device, which may signal the MIT device to activatea higher power radio interface. A message may be received from anassociated device (e.g., a paired device or a device associated with thesame or a related user account, such as wireless station 106, wirelessnode 107, and/or AP 112) or from an unassociated device (e.g., a deviceassociated with a different user account). In some embodiments, the MITdevice may not transmit regularly (e.g., continuously or periodically)while in the low power mode to conserve battery power. Further, the scanwindow period (e.g., the width of the window) and interval (e.g., theperiod between intervals) may be set or may be dynamically adjusted,e.g., in response to one or more factors, such as battery level,congestion/interference, time of day, sensor data, and so forth.Additionally, the MIT device may respond to a message addressed uniquelyto the MIT device, addressed to a group (or set) that includes the MITdevice, or addressed to all MIT devices. The MIT device also may ignoremessages that are not addressed to the MIT device, e.g., such asmessages uniquely addressed to a different MIT device or to a group towhich the MIT device does not belong.

At 1304, the MIT device may activate at least one higher powerinterface, e.g., based on detected motion and/or a message receivedduring a scan window. At 1306, the MIT device can determine whether itspresent location corresponds to a safe zone, a risk zone, or some otherdefined zone. A zone (or region) can be any bounded or defined space(e.g., a geo-fenced area). At 1308, the MIT device may adapt itsbehavior based on the determined zone. For example, when the MIT devicedetermines that it is in a safe zone, the MIT device can enter a lowpower mode and select scan window settings that will allow the MITdevice to enhance power conservation. In some implementations, MITdevice operating settings can be dynamically adjusted to achieve atarget operating duration, such as 6 months, 9 months, 12 months, 18months, 24 months, 36 months, and so forth. As another example, when theMIT device determines that it is in a risk (or danger) zone, e.g., in atransit scenario, the MIT device can select scan window settings thatwill allow the MIT device to more quickly identify a message (e.g.,longer, more frequent scan windows) and can optionally activate a higherpower interface (e.g., BT/BLE) to actively transmit beacons. The riskzone MIT device settings can be maintained until the MIT devicedetermines an exit event, such as leaving a risk zone, entering a safezone, determining that it is lost (e.g., after no contact has been madewith another device for a threshold period of time and/or being locatedoutside of a known zone).

At 1310, the MIT device may return to a low power mode once a triggercondition has been satisfied. For example, after establishing contactwith another device, after conducting a successful location updateoperation, after returning to a safe zone, upon motion stopping, upondetecting an associated device in proximity, etc. the MIT device canreturn to a lower power mode of operation.

Turning to FIG. 14, at 1402, an MIT device (such as MIT device 108)having any/all of a low power radio interface (e.g., a wake-up radioand/or wake-up receiver), a medium power radio interface (e.g.,Bluetooth (BT) and/or Bluetooth Low Energy (BLE)), and/or a high powerradio interface (e.g., UWB, 60 GHz) may be in a low power mode ofoperation (e.g. operating in a low power mode of operation). In the lowpower mode, the MIT device, via the low power radio interface, mayperiodically scan for messages (e.g., beacons, polls, probes, etc.)addressed to the MIT device, which may signal the MIT device to activatea higher power radio interface. A message may be received from anassociated device (e.g., a paired device or a device associated with thesame or a related user account, such as wireless station 106, wirelessnode 107, and/or AP 112) or from an unassociated device (e.g., a deviceassociated with a different user account). In some embodiments, the MITdevice may not transmit regularly (e.g., continuously or periodically)while in the low power mode to conserve battery power. Further, the scanwindow period (e.g., the width of the window) and interval (e.g., theperiod between intervals) may be set or may be dynamically adjusted,e.g., in response to one or more factors, such as battery level,congestion/interference, time of day, sensor data, and so forth.Additionally, the MIT device may respond to a message addressed uniquelyto the MIT device, addressed to a group (or set) that includes the MITdevice, or addressed to all MIT devices. The MIT device also may ignoremessages that are not addressed to the MIT device, e.g., such asmessages uniquely addressed to a different MIT device or to a group towhich the MIT device does not belong.

At 1404, the MIT device may activate at least one higher powerinterface, e.g., based on detected motion and/or a message receivedduring a scan window. At 1406, the MIT device can determine that it islost (e.g., in a lost condition). For example, the MIT device candetermine that it has not been in contact with another device for morethan a threshold duration and/or is located outside of a known zone. At1408, in response to determining that it is lost, the MIT device cantransition to a mode in which at least one higher power interface isperiodically activated (e.g., adapt behavior based on the lostcondition). For example, the MIT device can activate the medium powerinterface (e.g., BT/BLE) and can transmit one or more beaconsperiodically. The beacon period, beacon interval, and number of beaconstransmitted can be selected to conserve power, to increase theprobability of discovery, or both. Further, the transmit power for oneor more beacons can be varied. For example, beacon transmit power can bevaried cyclically (e.g., −25 dBm, −10 dBm, 0 dBm, +4 dBm) to covervarious ranges. Any number of different transmit power values can beused and the powers shown are only exemplary.

Further, the number and values of transmit power used, as well as thetiming, can be varied based on a variety of factors, such as remainingbattery power, time of day, amount of light, length of time since lastcontact with another device, etc. For example, more aggressive beaconingcan be performed while sufficient battery power remains (e.g., above50%, between 50% and 20%, above 10%, etc.). More aggressive beaconingalso can be performed at times when people are more likely to be present(e.g., based on the MIT device's clock, an embedded light sensor,detected RF signals, etc.). Similarly, the MIT device can transition tomore conservative beaconing, e.g., when battery power falls below apredetermined level, during periods when people are less likely to bepresent, etc.

At 1410, the MIT device may return to a low power mode once a triggercondition has been satisfied. For example, after establishing contactwith another device, after conducting a successful location updateoperation, after returning to a safe zone, upon motion stopping, upondetecting an associated device in proximity, etc. the MIT device canreturn to a lower power mode of operation.

FIG. 15 illustrates an example method of scanning for an MIT device,according to some embodiments. The method shown in FIG. 15 may be usedin conjunction with any of the systems or devices shown in the Figures,among other devices. In various embodiments, some of the method elementsshown may be performed concurrently, in a different order than shown, ormay be omitted. Additional method elements may also be performed asdesired. As shown, this method may operate as follows.

At 1502, a wireless device (such as wireless station 106, wireless node107, and/or AP 112) may transmit a message to one or more MIT devices(or tags, transponders, etc., such as MIT device 108). The wirelessdevice can be associated with one or more of the MIT devices. Forexample, the device may be a companion device (e.g., a phone or mobilecomputing device) associated with a user account that also is associatedwith the one or more MIT devices (a common user account) or previouslypaired with the MIT device. The wireless device can address the messageto a specific MIT device (e.g., associated with an object to belocated), a set of MIT devices (e.g., of a common type or linked throughan association), or generally to all MIT devices. Further, the messagecan be transmitted using an interface that can be received by alow-power interface of the MIT device (e.g., a wake-up radio and/orwake-up receiver).

At 1504, wireless device may establish communications with an MIT deviceof the one or more MIT devices over a medium power interface. Note thatin some embodiments, upon receiving the message, the MIT device mayactivate the medium power (and range) interface, such as a Bluetooth(BT) or BT low-energy (BLE) interface. In some instances, the wirelessdevice can utilize communications over the medium power interface tolocate the MIT device. For example, the wireless device can instruct theMIT device to output one or more signals, such as audible signals,visual signals (e.g., a light), and/or haptic signals. Additionally oralternatively, the wireless device and the MIT device can use signalinformation (e.g., signal strength measurements (RSSI)) to perform thelocation operation. In other instances, the wireless device may instructthe MIT device to activate a high power interface, such as a UWBinterface, to provide more precise location information (e.g., ascompared to other methods of determining location of the MIT device). Insome embodiments, the wireless device and the MIT device can use asingle interface or multiple interfaces for the location operation.

At 1506, the wireless device may present a location interface, e.g., ona display. The location interface can be a live image (e.g., a camerafeed) or a rendering (e.g., a map, blank screen, etc.) and may alsoinclude one or more location indicators corresponding to the location ofthe MIT device. For example, one or more arrows, dots, circles, or othersuch indicators. Further, the one or more location indicators can vary,e.g., in size, color, shape, and/or intensity, to provide furtherinformation regarding the location of the MIT device. In someembodiments, the wireless device may only present the location interfacewhen the high power interface is active.

At 1508, once the location of the MIT device has been determined (e.g.,through the high power interface), the wireless device may transmit oneor more messages instructing the MIT device to deactivate the high powerinterface, e.g., to reduce battery consumption. Further, the wirelessdevice may instruct the MIT device to deactivate one or more otherinterfaces and/or to terminate one or more outputs (e.g., audible,visual, haptic). In addition, the instructions may direct the MIT deviceto return to a lower-power mode of operation, e.g., periodicallyscanning for a wake-up signal via the low power interface (e.g., wake-upradio and/or wake-up receiver).

MIT Device Use Embodiments

In some embodiments, a multi-interface transponder (MIT) device, such asMIT device 108, may be used as a monetary device, e.g., for moneytransfer and/or as a payment apparatus. For example, an MIT device maybe used to transfer money, acting as a stored-value card or acash-on-card, such as a prepaid transit card, gift card, or other suchcard implementation. For example, the MIT device can include a secureprocessor and/or secure storage in addition to communication circuitry,one or more sensors, processors, memories, a power source, etc. In suchembodiments, the MIT device may operate in a stand-alone mode (or as astand-alone device), e.g., without a companion device. In someembodiments, the MIT device may be associated with an account (e.g., abank account, such as a credit card, debit card, checking and/or savingsaccount) or monetary pool (e.g., such as a pre-funded account hosted bya service, but not directly associated with a bank account). In someembodiments, the MIT device may be enabled to use an ultra-widebandinterface for “tap to pay” operations, thereby allowing for a high levelof transaction security. In some embodiments, the MIT device may beimplemented as a lending device, e.g., enabled to lend money via athird-party service, such as Venmo, PayPal, Apple Pay and so forth.

As another example, the MIT device may be attached to (or associatedwith) an article to be shared amongst a community of users, such asbetween neighbors within a neighborhood and/or between members of asocial group. In some embodiments, the MIT device may aid in tracking ofthe article (e.g., last user, last and/or current location) as well asmaintaining information associated with the article (e.g., users,locations, amount of usage, and so forth). Similarly, the MIT device maybe implemented for inventory tracking (e.g., attached/associated witharticles typically assigned or shared with users) for companies, sportsteams, communities, and so forth.

In some embodiments, a multi-interface transponder (MIT) device, such asMIT device 108, may be used as a form of identification, e.g., forvalidation of visitors. For example, in some embodiments, an MIT devicemay become a digital representation of a person's identity. In someembodiments, the MIT device, e.g., in a secure memory, can storeauthentication information, such as a token. Further, the authenticationinformation may be encrypted in a manner that allows for securedecryption and authentication. The representation may includedescription, images, current location, and/or intended location of theperson. In some embodiments, a user may can scan for an MIT device andconfirm location of the MIT device and the person's identity. Forexample, upon scanning for the MIT device (e.g., via a wireless devicesuch as an AP 112, a wireless station 106, and/or a wireless node 107,the user may be provided with information to confirm the identity of theperson, such as a photo identify the person, a log of the person'sintended location, and so forth). In some embodiments, scanning may beimplemented via a home security system, e.g., for identity confirmationand/or to authorize entry, or conversely, to not authorize entry andnotify security. As another example, the MIT device may be implementedat part of a chain of trust, e.g., to allow in store pickups of onlineorders, signing for received shipments, and so forth.

Further Embodiments

In some embodiments, a multi-interface transponder device (MIT), e.g.,as described herein, may include one or more radios (e.g., forsupporting interfaces), at least one antenna, a memory, and one or moreprocessors (e.g., processing circuitry, processing elements, and soforth). In some embodiments, the one or more radios may include one ormore of a Bluetooth (BT) radio (e.g., any radio supporting various formsof Bluetooth, including Bluetooth Low Energy), an ultra-wideband (UWB)radio, and/or an ultra-low power radio (e.g., such as a wake-up radioand/or wake-up receiver). Additionally, in some embodiments, the MITdevice may include motion sensing circuitry (e.g., a gyroscope, anaccelerometer, and/or any of various other motion sensing components).

In some embodiments, the MIT device may be configured to:

enter a low power mode in which the second radio is disabled;

receive, while in the low power mode, a wake-up signal from aneighboring wireless device; and

transmit, after transitioning to a higher power mode in response toreceipt of the wake-up signal, beacons via the second radio, wherein thesecond radio is enabled in the higher power mode. In some embodiments,the wake-up signal may be received by an ultra-low power radio, e.g.,via ULP/LP communications with the neighboring wireless device.

In some embodiments, the neighboring wireless device may comprise acompanion device. In some embodiments, the companion device may haveassisted the MIT device with registration with a location server. Insome embodiments, the companion device and the MIT device may beassociated with the location server. In some embodiments, the MIT may beconfigured to:

receive, from the neighboring wireless device, an indication that alocation associated with the MIT device has been updated at the locationserver; and

transition, based, at least in part, on the indication, to the low powermode.

In some embodiments, the wakeup signal may indicate a transmission rate.In some embodiments, the transmission rate may be based, at least inpart, on one or more of a transportation mode detected by theneighboring wireless device and/or an expected medium congestion asdetected by the neighboring wireless device. In some embodiments, thewakeup signal may indicate a transmission power. In some embodiments,the transmission power may be based, at least in part, on one or more ofa transportation mode detected by the neighboring wireless device and/oran expected medium congestion as detected by the neighboring wirelessdevice.

In some embodiments, the second radio may comprise an ultra-widebandradio.

In some embodiments, the neighboring wireless device may comprise anon-companion device. In some embodiments, the non-companion device andthe MIT device may be associated with a location server.

In some embodiments, the wakeup signal may be received via the firstradio. In some embodiments, the first radio may comprise one of aBluetooth radio and/or an ultra-low power radio (e.g., such as a wake-upradio and/or wake-up receiver).

In some embodiments, the MIT may be further configured to determine afirst condition of the MIT device based, at least in part, on a durationof time since communication with a companion device and transition to alost mode of operation based on the first condition. In someembodiments, the companion device may have assisted the MIT device withregistration with a location server. In some embodiments, the companiondevice and the MIT device may be associated with the location server. Insome embodiments, when in the lost mode of operation, the MIT device maybe configured to transmit, via the first radio, beacons at a firstperiodic interval during a first portion of a day and transmit, via thefirst radio, beacons at a second periodic interval during a secondportion of the day. In some embodiments, he first portion of the day mayat least partially correspond to daylight hours and the second portionof the day may at least partially correspond to non-daylight hours. Insome embodiments, the second periodic interval may longer than the firstperiodic interval. In some embodiments, the MIT device may be configuredto increase transmission power for beacons transmitted via the firstradio, based, at least in part on one of the duration of time or time ofday. In some embodiments, the first radio may comprise a Bluetoothradio. In some embodiments, the first condition of the MIT device may befurther based, at least in part, on a duration of time since anindication of a location update or reception of a signal from aneighboring wireless device.

In some embodiments, the MIT device may be configured to:

operate in a low power mode in which an ultra-wide band (UWB) radio incommunication with the at least one processor is disabled;

receive, while operating in the low power mode, a wake-up signal from aneighboring wireless device;

generate instructions to transition out of the low power mode and enablethe UWB radio in response to receipt of the wake-up signal; and

generate instructions to transmit, via the UWB radio, location beaconsto the neighboring wireless device. In some embodiments, the wake-upsignal may be received by an ultra-low power radio, e.g., via ULP/LPcommunications with the neighboring wireless device.

In some embodiments, the wakeup signal may be received via one of aBluetooth radio or an ultra-low power radio (e.g., such as a wake-upradio and/or wake-up receiver) in communication with the at least oneprocessor.

In some embodiments, the wakeup signal may indicate a transmission rateand a transmission power for the location beacons.

In some embodiments, the MIT device may be further configured to:

receive, from the neighboring wireless device an indication that alocation associated with the MIT device has been updated at a locationserver; and

generate instructions to transition to the low power mode and disablethe UWB radio.

In some embodiments, the wakeup signal may indicate a transmission rateand a transmission power for the location beacons. In some embodiments,each of the transmission rate and the transmission power may be based,at least in part, on one or more of a transportation mode detected bythe neighboring wireless device and/or an expected medium congestion asdetected by the neighboring wireless device.

In some embodiments, the MIT device may be configured to:

broadcast location beacons at a first transmission rate and firsttransmission power;

increase, in response to detection of a trigger condition, the firsttransmission rate to a second transmission rate; and

broadcast location beacons at the second transmission rate and firsttransmission power.

In some embodiments, the trigger condition may comprise receipt of anindication that a companion device has moved more than a thresholddistance from the MIT device. In some embodiments, the indication may bereceived via the first radio and location beacons may be transmitted viathe second radio. In some embodiments, the threshold distance may beapproximately 1 meter.

In some embodiments, the MIT device may be configured to:

receive, from a companion device, an indication to increase transmissionpower to a second transmission power, wherein the indication is based,at least in part, on medium congestion; and

transmit, to the companion device, location beacons at the secondtransmission power.

In some embodiments, prior to broadcasting location beacons at the firsttransmission rate and first transmission power, the MIT device may beconfigured to:

receive, while operating in a low power mode, an indication of atransition in transportation mode from a companion device, wherein thesecond radio is disabled in the low power mode; and

transition, based on the indication, to a higher power mode, wherein thesecond radio is enabled in the higher power mode.

In some embodiments, the MIT device may be configured to:

receive, from the companion device, an indication of an end of atransition in a transportation mode; and

transition, in response to the indication, back to the low power state.

In some embodiments, the trigger condition may comprise detection of atransition in a transportation mode. The transition may comprise astopping of the mode of transportation. In some embodiments, thedetermination may be based on a change in velocity of the MIT device.

In some embodiments, the MIT device may be configured to:

determine, while in a first power state, to transition to a second powerstate based, at least in part, on detection of an event detectable viaone of a first interface (e.g., supported by a first radio of the one ormore radios) and/or motion sensing circuitry of the MIT device;

transition from the first power state to the second power state;

transmit, while in the second power state, one or more beacons via oneof a second interface (e.g., supported by a second radio of the one ormore radios) or a third interface (e.g., supported by a third radio ofthe one or more radios) of the MIT device;

receive, from a neighboring wireless device while in the second powerstate, an indication that a location associated with the MIT device hasbeen updated at a location server; and

determining to transition, based, at least in part, on the indication,to a third power state.

In some embodiments, selection of the second interface or thirdinterface may be based, at least in part, on the detected event. In someembodiments, the neighboring wireless device and the MIT device may eachbe associated with the location server.

In some embodiments, the first interface may be an ultra-low power radiofrequency (RF) interface (e.g., such as a wake-up radio and/or wake-upreceiver). In other words, the first radio, in some embodiments, may bean ultra-low power radio. In some embodiments, the first interface maybe a Bluetooth (BT) interface. Thus, in such embodiments, the firstradio may be a Bluetooth radio.

In some embodiments, the second interface may be one of a Bluetoothinterface and an ultra-wideband (UWB) radio frequency (RF) interface andthe third interface may be one of a (BT) Bluetooth interface and an UWBRF interface. In other words, the second and third radios, in someembodiments, may be one of a BT radio and/or a UWB radio.

In some embodiments, the event detectable via the first interface mayinclude receiving a wakeup signal from a companion device. In someembodiments, the wakeup signal may include instructions fortransitioning to the second power state. In some embodiments, theinstructions may indicate that the MIT device activates the thirdinterface, e.g., when the third interface includes an UWB RF interface.In some embodiments, the instructions may indicate that the MIT deviceactivates the second interface, e.g., when the second interfacecomprises a BT interface.

In some embodiments, the instructions may indicate a transmission rate.In some embodiments, the transmission rate may be based, at least inpart, on a transportation mode detected by the companion device. In someembodiments, the transmission rate may be based, at least in part, onexpected medium congestion as detected by the companion device.

In some embodiments, the instructions may indicate a transmission power.In some embodiments, the transmission power may be based, at least inpart, on a transportation mode detected by the companion device. In someembodiments, the transmission power may be based (and/or further based),at least in part, on expected medium congestion as detected by thecompanion device.

In some embodiments, the neighboring wireless device may be a companiondevice that may have assisted the MIT device with registration with thelocation server. In some embodiments, the neighboring wireless devicemay be a non-companion device that may be associated with the locationserver.

In some embodiments, the MIT device may be configured to:

determine a first condition of the MIT device based, at least in part,on a duration of time since communication with a companion device; and

transition to a first mode of operation based on the first condition.

In some embodiments, the first mode of operation may include any, anycombination of, and/or all of transmitting beacons over a firstinterface at a first periodic interval during a first portion of a day,transmitting beacons over the first interface at a second periodicinterval during a second portion of the day, and/or increasingtransmission power for beacons, based, at least in part on one of theduration of time and/or time of day. In some embodiments, the firstportion of the day may at least partially correspond to daylight hours.In some embodiments, the second portion of the day may at leastpartially correspond to non-daylight hours. In some embodiments, thesecond periodic interval may be longer than the first periodic interval.

In some embodiments, the first condition of the MIT device may befurther based, at least in part, on a duration of time since anindication of a location update and/or reception of a signal from aneighboring device.

In some embodiments, the first periodic interval may be adjusted based,at least in part, on transmit power.

In some embodiments, the MIT device may be further configured to:

receive a signal from a neighboring wireless device; and

increase transmission frequency and/or transmission power in response toreceiving the signal.

In some embodiments, the first mode of operation may further include apower conservation period. In some embodiments, the power conservationperiod may at least 10 times longer than the first or second portions ofthe day. In some embodiments, the power conservation period may be atleast 100 times longer than the first or second portions of the day. Insome embodiments, the power conservation period may be at least 1000times longer than the first or second portions of the day.

In some embodiments, the first interface may be a Bluetooth interface.

In some embodiments, the MIT device may be configured to:

receive, via a first interface and while in a first power state, anindication of a transition in transportation mode from a companiondevice;

transition, in response to the indication, to a second power state; andtransmitting, over a second interface, one or more beacons at a firsttransmission rate and first transmission power to the companion device.

In some embodiments, transitioning to the second power state mayactivate the second interface. In some embodiments, the second interfacemay consume more power than the first interface.

In some embodiments, the first interface may be an ultra-low powerwakeup radio frequency interface. In some embodiments, the secondinterface may one of a Bluetooth interface or ultra-wideband RFinterface.

In some embodiments, the MIT device may be further configured to:

receive, from the companion device, an indication of an end of thetransition in transportation mode; and

transition, in response to the indication, back to the first powerstate.

In some embodiments, the MIT device may be further configured to:receive, from the companion device, an indication that the companiondevice has moved more than a threshold distance from the MIT device; and

increase, in response to the indication, transmission rate of the one ormore beacons.

In some embodiments, the threshold distance may be approximately 1meter. In some embodiments, the threshold distance may be greater than 2feet but less than 3 feet.

In some embodiments, the MIT device may be further configured toreceive, from the companion device, an indication to increasetransmission power, wherein the indication is based, at least in part,on medium congestion.

In some embodiments, the companion device may be at least one of a userequipment device or a wearable device.

In some embodiments, the transportation mode may include at least one ofa vehicle, a train, a boat, or a plane.

In some embodiments, a wireless device, such as a client station and/ora wireless node, e.g., as described herein, may be configured as acompanion device to a multi-interface transponder (MIT) device, e.g., asdescribed herein. The wireless device may include may include one ormore radios (e.g., for supporting one or more interfaces), at least oneantenna, a memory, and one or more processors (e.g., processingcircuitry, processing elements, and so forth). In some embodiments, theone or more radios may include one or more of a Bluetooth (BT) radio(e.g., any radio supporting various forms of Bluetooth, includingBluetooth Low Energy), an ultra-wideband (UWB) radio, an ultra-low powerradio (e.g., such as a wake-up radio and/or wake-up receiver), and/or acellular radio. Additionally, in some embodiments, the wireless devicemay include motion sensing circuitry (e.g., a gyroscope, anaccelerometer, and/or any of various other motion sensing components).

In some embodiments, the wireless device may be configured to:

transmit, to an MIT device, instructions to activate an ultra-widebandinterface;

receive, from the MIT device, one or more signals via ultra-widebandcommunications;

determine, based on the received one or more signals, a location of theMIT device relative to the wireless device;

display, via a user interface, an indication of the location of the MITdevice relative to the wireless device; and

update, based on movement of the wireless device, the location of theMIT device relative to the wireless device.

In some embodiments, the instructions may be transmitted via anultra-low power radio frequency signal.

In some embodiments, the indication may be displayed via a map displayedon a display of the wireless device.

In some embodiments, the indication may include an augmented realityrendering of the location of the MIT device relative to the wirelessdevice.

In some embodiments, the wireless device may be further configured to,in response to determining the location of the MIT device, transmitinstructions to the MIT device to deactivate the ultra-widebandinterface of the MIT device. In some embodiments, the wireless devicemay be further configured to, in response to determining the location ofthe MIT device, transmit a location update message to a location server.

As described above, one aspect of the present technology is thegathering and use of data available from specific and legitimate sourcesto track and/or update a location of a multi-interface transponder (MIT)device. The present disclosure contemplates that in some instances, thisgathered data may include personal information data that uniquelyidentifies or can be used to identify a specific person. Such personalinformation data can include demographic data, location-based data,online identifiers, telephone numbers, email addresses, home addresses,data or records relating to a user's health or level of fitness (e.g.,vital signs measurements, medication information, exercise information),date of birth, or any other personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, tracking and/or updating location of an MITdevice may aid the user in maintaining location of various items ofimportance, such as keys, luggage, musical equipment, sports equipment,backpacks, briefcases, and the like.

The present disclosure contemplates that those entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities would beexpected to implement and consistently apply privacy practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. Such informationregarding the use of personal data should be prominent and easilyaccessible by users, and should be updated as the collection and/or useof data changes. Personal information from users should be collected forlegitimate uses only. Further, such collection/sharing should occur onlyafter receiving the consent of the users or other legitimate basisspecified in applicable law. Additionally, such entities should considertaking any needed steps for safeguarding and securing access to suchpersonal information data and ensuring that others with access to thepersonal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations that may serve to imposea higher standard. For instance, in the US, collection of or access tocertain health data may be governed by federal and/or state laws, suchas the Health Insurance Portability and Accountability Act (HIPAA);whereas health data in other countries may be subject to otherregulations and policies and should be handled accordingly.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing identifiers, controlling the amount orspecificity of data stored (e.g., collecting location data at city levelrather than at an address level), controlling how data is stored (e.g.,aggregating data across users), and/or other methods such asdifferential privacy.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users based on aggregated non-personalinformation data or a bare minimum amount of personal information, suchas the content being handled only on the user's device or othernon-personal information available to the content delivery services.

Embodiments of the present disclosure may be realized in any of variousforms. For example, some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Other embodiments may berealized using one or more programmable hardware elements such as FPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of the methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a wireless device may be configured to include aprocessor (or a set of processors) and a memory medium, where the memorymedium stores program instructions, where the processor is configured toread and execute the program instructions from the memory medium, wherethe program instructions are executable to cause the wireless device toimplement any of the various method embodiments described herein (or,any combination of the method embodiments described herein, or, anysubset of any of the method embodiments described herein, or, anycombination of such subsets). The device may be realized in any ofvarious forms.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

What is claimed is:
 1. A multi-interface transponder (MIT) device,comprising: a first radio comprising circuitry supporting at least afirst radio access technology (RAT); a second radio comprising circuitrysupporting at least a second RAT; and one or more processors coupled tothe first radio and the second radio; wherein the one or more processorsare configured to cause the MIT device to: broadcast location beacons ata first transmission rate and first transmission power; increase, inresponse to detection of a trigger condition, the first transmissionrate to a second transmission rate; and broadcast location beacons atthe second transmission rate and first transmission power.
 2. The MITdevice of claim 1, wherein the trigger condition comprises receipt of anindication that a companion device has moved more than a thresholddistance from the MIT device.
 3. The MIT device of claim 2, wherein theindication is received via the first radio; and wherein location beaconsare transmitted via the second radio.
 4. The MIT device of claim 2,wherein the threshold distance is approximately 1 meter.
 5. The MITdevice of claim 1, wherein the one or more processors are furtherconfigured to cause the MIT device to: receive, from a companion device,an indication to increase transmission power to a second transmissionpower, wherein the indication is based, at least in part, on mediumcongestion; and transmit, to the companion device, location beacons atthe second transmission power.
 6. The MIT device of claim 1, wherein,prior to broadcasting location beacons at the first transmission rateand first transmission power, the one or more processors are furtherconfigured to cause the MIT device to: receive, while operating in a lowpower mode, an indication of a transition in transportation mode from acompanion device, wherein the second radio is disabled in the low powermode; and transition, based on the indication, to a higher power mode,wherein the second radio is enabled in the higher power mode.
 7. The MITdevice of claim 6, wherein the one or more processors are furtherconfigured to cause the MIT device to: receive, from the companiondevice, an indication of an end of a transition in a transportationmode; and transition, in response to the indication, back to the lowpower mode.
 8. The MIT of claim 1, wherein the trigger conditioncomprises detection of a transition in a mode of transportation, whereinthe transition comprises a stopping of the mode of transportation, andwherein the trigger condition is based on a change in velocity of theMIT device.
 9. An apparatus comprising: a memory; and at least oneprocessor in communication with the memory; wherein the at least oneprocessor is configured to: generate instructions to broadcast locationbeacons at a first transmission rate; increase, in response to detectionof a trigger condition, the first transmission rate to a secondtransmission rate, wherein the trigger condition comprises as least oneof: a transition in transportation mode; a companion device moving morethan a threshold distance from the apparatus; or detection of a changein velocity of the apparatus; and broadcast location beacons at thesecond transmission rate.
 10. The apparatus of claim 9, wherein thethreshold distance is approximately 1 meter.
 11. The apparatus of claim9, wherein, prior to generating instructions to broadcast locationbeacons at the first transmission rate and first transmission power, theat least one processor is further configured to: receive, whileoperating in a low power mode, an indication of the transition intransportation mode from a companion device, wherein the indication isreceived via a lower power radio in communication with the at least oneprocessor, wherein the lower power radio is at least one of an ultra-lowpower radio, a low power radio, or a Bluetooth radio, and wherein ahigher power radio in communication with the at least one processor isdisabled in the low power mode, wherein the higher power radio comprisesat least one of a Bluetooth radio, a wideband radio, or anultra-wideband radio; and transition, based on the indication, to ahigher power mode, wherein the higher power radio is enabled in thehigher power mode, and wherein location beacons are broadcast via thehigher power radio.
 12. The apparatus of claim 11, wherein the lowerpower radio is deactivated in the higher power mode.
 13. The apparatusof claim 9, wherein the transition in transportation mode comprises atleast one of: detection of a known transportation transition point; ordetection of a known transportation destination.
 14. The apparatus ofclaim 9, wherein the at least one processor is further configured to:receive, from a companion device, an indication of an end of the triggercondition; and in response to the indication, generate instructions tobroadcast location beacons at the first transmission rate.
 15. Anon-transitory computer readable memory medium storing programinstructions executable by processing circuitry of a multi-interfacetransponder (MIT) device to: broadcast, to one or more neighboringwireless devices, location beacons at a first transmission rate;increase, in response to a trigger indication, the first transmissionrate to a second transmission rate; and transmit, to the one or moreneighboring wireless devices, location beacons at the secondtransmission rate.
 16. The non-transitory computer readable memorymedium of claim 15, wherein the trigger indication comprises as leastone of: detection of a transition in transportation mode; detection of acompanion device moving more than a threshold distance from the MIT,wherein the companion device is included in the one or more neighboringwireless devices; or detection of a change in velocity of the MIT. 17.The non-transitory computer readable memory medium of claim 16, whereinthe threshold distance is approximately 1 meter.
 18. The non-transitorycomputer readable memory medium of claim 16, wherein, to detect thetransition in transportation mode, the program instructions are furtherexecutable to perform at least one of: receiving an indication of thetransition from the companion device; detecting arrival at a knowntransportation transition point; or detecting arrival at a knowntransportation destination.
 19. The non-transitory computer readablememory medium of claim 15, wherein the program instructions are furtherexecutable to: receive, from a companion device, an indication toincrease transmission power to a second transmission power, wherein theindication is based, at least in part, on medium congestion, and whereinthe companion device is included in the one or more neighboring wirelessdevices; and transmit, to the companion device, location beacons at thesecond transmission power.
 20. The non-transitory computer readablememory medium of claim 15, wherein the program instructions are furtherexecutable to: receive, from a companion device, an indication of an endof a trigger condition, wherein the companion device is included in theone or more neighboring wireless devices; and in response to theindication, generate instructions to broadcast location beacons at thefirst transmission rate.